Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • 1000 entries must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Felled date Entry date Start date End date
701 34/96 217025622 EARLS COURT ROAD

Unexpected geom type

2025-01-03
702 02-Apr 217026023 EARLS COURT ROAD

Unexpected geom type

2025-01-03
703 K32 217026337 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
704 K32 217107397 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
705 17/74 217026337 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
706 Aug-81 217026446 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
707 Aug-81 217026430 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
708 Aug-81 217026421 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
709 Aug-81 217026403 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
710 Aug-81 217026378 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
711 Aug-81 217026377 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
712 Aug-81 217026358 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
713 Jan-78 217026787 EARLS COURT SQUARE

Unexpected geom type

2025-01-03
714 K16 217107336 EARLS TERRACE

Unexpected geom type

2025-01-03
715 K16 217026896 EARLS TERRACE

Unexpected geom type

2025-01-03
716 Jun-72 217026912 EARLS TERRACE

Unexpected geom type

2025-01-03
717 Jun-72 217026919 EARLS TERRACE

Unexpected geom type

2025-01-03
718 Aug-86 217026923 EARLS WALK

Unexpected geom type

2025-01-03
719 24/75 217115087 EDITH GROVE

Unexpected geom type

2025-01-03
720 24/75 217027161 EDITH GROVE

Unexpected geom type

2025-01-03
721 24/75 217027170 EDITH GROVE

Unexpected geom type

2025-01-03
722 24/75 217027175 EDITH GROVE

Unexpected geom type

2025-01-03
723 24/75 217027320 EDITH GROVE

Unexpected geom type

2025-01-03
724 24/75 217027342 EDITH GROVE

Unexpected geom type

2025-01-03
725 24/75 217027350 EDITH GROVE

Unexpected geom type

2025-01-03
726 24/75 217027356 EDITH GROVE

Unexpected geom type

2025-01-03
727 24/75 217027218 EDITH GROVE

Unexpected geom type

2025-01-03
728 24/75 217027221 EDITH GROVE

Unexpected geom type

2025-01-03
729 24/75 217027222 EDITH GROVE

Unexpected geom type

2025-01-03
730 Aug-98 217027309 EDITH GROVE

Unexpected geom type

2025-01-03
731 24/75 217027571 EDITH TERRACE

Unexpected geom type

2025-01-03
732 13/99 217027497 EDITH TERRACE

Unexpected geom type

2025-01-03
733 K14 217027584 EDWARDES PLACE

Unexpected geom type

2025-01-03
734 K14 217027588 EDWARDES PLACE

Unexpected geom type

2025-01-03
735 Jun-72 217027637 EDWARDES SQUARE

Unexpected geom type

2025-01-03
736 K16 217027639 EDWARDES SQUARE

Unexpected geom type

2025-01-03
737 K16 217027640 EDWARDES SQUARE

Unexpected geom type

2025-01-03
738 Jun-72 217027641 EDWARDES SQUARE

Unexpected geom type

2025-01-03
739 K16 217027642 EDWARDES SQUARE

Unexpected geom type

2025-01-03
740 K16 217027646 EDWARDES SQUARE

Unexpected geom type

2025-01-03
741 K16 217027647 EDWARDES SQUARE

Unexpected geom type

2025-01-03
742 K16 217027649 EDWARDES SQUARE

Unexpected geom type

2025-01-03
743 Jun-72 217027661 EDWARDES SQUARE

Unexpected geom type

2025-01-03
744 K16 217027656 EDWARDES SQUARE

Unexpected geom type

2025-01-03
745 K16 217107329 EDWARDES SQUARE

Unexpected geom type

2025-01-03
746 Jul-85 217027667 EDWARDES SQUARE

Unexpected geom type

2025-01-03
747 Feb-80 217027650 EDWARDES SQUARE

Unexpected geom type

2025-01-03
748 K52 217027698 EGERTON CRESCENT

Unexpected geom type

2025-01-03
749 K52 217027699 EGERTON CRESCENT

Unexpected geom type

2025-01-03
750 K52 217027728 EGERTON CRESCENT

Unexpected geom type

2025-01-03

Showing rows 701 to 750 of 1000

How to fix this issue

Your dataset is missing the geometry column.

The Tree guidance explains how to fix the issue:

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL